Data Alignment between Army C4I Databases and Army Simulations

C4I Interfaces to Simulations are limited in functionality. One of the principle factors causing this is a lack of interface standards. While standards are a necessary condition, they are not sufficient. In order to have a complete interface, the data to be exchanged must be represented in both systems (C4I and Simulation). However, the current status is that C4I systems and simulations 1) do not contain the same data elements; 2) represent data differently, and 3) are often unaware of the other’s data requirements. The Joint Technical Architecture-Army (JTAArmy) mandates use of specific data models for certain classes of information systems (such as tactical C4I systems). Simulation developers should be cognizant of these data models in the development of new Army Simulations. The Army is using a common data base, the Joint Common Data Base (JCDB,) in it’s Army Battle Command Systems (ABCS). In order to interface effectively to Army C4I systems, simulations must represent the critical data elements that are 1) used to initialize the JCDB; and 2) sent between the simulations and C4I systems. However, often Army simulations do not contain these critical data elements which will result in functionality that must be provided by interfaces. Each data element that does not have an exact match on the simulation side causes a translation/transformation to occur, with resulting cost and complexity. Since any interface must align any differences, the interface can become quite complex. This paper compares an Army C4I Data Model of the JCDB to a simulation representation (an Army Modeling and Simulation Office proposed standard that is representative of current and future simulations) to identify areas which are not aligned. Results of this analysis show that current Army representations are not aware of the standard data models that will be used in future Army ABCS systems.